Installation Guide for Seagate Crystal Reports and Seagate Info Connectivity to SAP R/3 System

Table Access Method

Last Revised May 7, 1999

Table of Contents

1.0	Introduction	3
2.0	Installation Overview	3
3.0	Installing the R/3 Client	3
4.0	Installing the Seagate Info and Seagate Crystal Reports Database Driver	4
5.0	Installing the Seagate Software ABAP/4 Functions and Tables	4
5.1	Copy the transport request files to the R/3 server’s transport directory	4
5.2	Add the transport request to the transport buffer on the server	4
5.3	Import the transport request	4
5.4	Verify a successful import	4
6.0	Troubleshooting	4
6.1	Troubleshooting server-side installation	4
6.2	Troubleshooting client problems	5
Appendix 1 - Sample Services File Entries for SAP	6

1.0	Introduction

This guide is intended to aid in the installation of the client and server components required for Seagate Crystal Reports or Seagate Info to connect to the transparent, cluster, pool, and view type tables in the SAP R/3 system.  Users familiar with Windows 95 or Windows NT, TCP/IP networking within these platforms and the SAP R/3 GUI should perform this installation process.

2.0	Installation Overview

There are three separate steps that need to be performed in order to achieve connectivity to R/3.  The first step is to install the components required for the client to connect to R/3.  If the SAP GUI is installed and you can connect to the R/3 system then you can skip this step – your client has all the necessary components.  The next step is to install on the client the drivers Seagate Crystal Reports and Seagate Info requires in order to read the data from the R/3 system.  This is done automatically for you when you run the setup.exe installation program.  It is assumed you have installed the standard Seagate Crystal Reports or Seagate Info package on this machine.  The final step is to install an ABAP/4 function group onto the R/3 server.
 
3.0	Installing the R/3 Client

Before proceeding with this step, ensure that your Windows 95 or Windows NT machine has been set up with TCP/IP networking and that it can successfully connect to the SAP R/3 server.  You will need to know the host name or IP address of the machine that the R/3 server resides on.  Consult your network administrator if you are missing this information.  To test your connection, do the following:

1.	Go to the command prompt.
2.	Type “ping server” where server is the name of the machine that the R/3 server resides on.
3.	If the result is “Bad IP Address”, try specifying the IP address of the server instead of the name.

If, after doing the above test, you continue to get “Bad IP Address” then you need to consult your network administrator to establish a valid TCP/IP connection from your client machine to your R/3 server machine.

The next component required for the client to connect to R/3 is correct entries in the services file.  This file is located on Windows 95 machines in the windows directory.  On Windows NT machines the file is located in the winnt\system32\drivers\etc directory.  Refer to Appendix A for a sample of this file’s contents.  Note that it is possible for different port numbers to be listed depending on your server configuration.  If no entries beginning with sap exist in your services file you should contact your SAP administrator for the correct entries or, if another machine can connect to R/3, you can take that services file and copy its sap entries to your services file.  As always, make a backup of the file before making modifications to it.

The final component required is the librfc32.dll.  It should be located in the windows\system directory on Windows 95 machines and in the winnt\system32 directory on Windows NT machines.  If this file does not exist, the installation program will copy one into one of the above locations for you.

4.0	Installing the Seagate Info and Seagate Crystal Reports Database Driver

Run the setup.exe program.  If you have already installed the R/3 server side function, just choose the client install.  Otherwise, choose the Full install to get both the client as well as the R/3 Server function that needs to be installed.  The installation program installs a database driver file called p2srfc.dll into the winnt\crystal directory if you are running Windows NT or the windows\crystal directory if you are running Windows 95.
5.0	Installing the Seagate Software ABAP/4 Functions and Tables
For connectivity between the database driver and the R/3 server, we must install a function group, ZIMG, onto the R/3 server.  This function group contains one or more function modules that the driver must call.  We must also transport some custom structures and transparent tables for use by the driver.  We have packaged these items into an R/3 transport that must be imported into your R/3 system via the correction and transport system.  In order to do this, you must have operating system-level access to the R/3 server.  Your R/3 server must also have the correction and transport system configured properly.  Note that the person performing this process should have reasonable working knowledge of the R/3 correction and transport system.

Steps to import the transport:
5.1	Copy the transport request files to the R/3 server’s transport directory
1.	Copy the file K900112.IMG from the \sap\server directory on the CD to the /usr/sap/trans/cofiles directory on the R/3 server.
2.	Copy the file R900112.IMG from the \sap\server directory on the CD to the /usr/sap/trans/data directory on the R/3 server.
5.2	Add the transport request to the transport buffer on the server
1.	From the /usr/sap/trans/bin directory of your R/3 server, execute the following command:  ‘tp addtobuffer imgk900112 <SID>‘, where <SID> is the system ID of your R/3 server.
5.3	Import the transport request
1.	From the /usr/sap/trans/bin directory of your R/3 server, execute the following command:  ‘tp import imgk900112 <SID>‘, where <SID> is the system ID of your R/3 server.
5.4	Verify a successful import
1.	Run the SAPGUI on a client machine and log on to your R/3 server.
2.	Select transaction SE09.
3.	From the frame on the right hand side of the screen, select ‘Successful Imports’ and click the ‘Display’ button.
4.	If the import was successful, you should find IMGK900112 in the list of successful imports.  You may expand it if you wish to see the specifics of the import, including a log of what was done and any errors/warnings that may have occurred. 
6.0	Troubleshooting
6.1	Troubleshooting server-side installation
If upon running ‘tp import…’ you receive the error message “Original object must not be replaced”, you have probably previously installed the ZIMG function group manually.  If this is the case, you must run tp again, telling it to ignore this error condition.  The syntax for this is ‘tp import IMGK900112 <SID> U2’.  (U2 specifies replace original objects.)
6.2	Troubleshooting client problems
If, when creating a report, you do not see the SAP button as a data source, check for the presence of the librfc32.dll and the p2srfc.dll on the client machine.  These are required for Seagate Crystal Reports and Seagate Info to communicate with the R/3 system.

If the login to SAP R/3 fails, check that you have specified the correct server information in the login dialog.  Also, if you specified the server name rather than the IP address, try specifying the IP address instead and vice versa.  If it still fails, the client portion of the installation may not have been successful.  See if you can connect through the SAPGUI on that machine.  If not, check that you can ping the machine the R/3 server is residing on.  Also, check that you have a valid services file on the client machine.

If the login succeeds but you don’t see any table names listed to choose from, the server portion of the installation may not have been successful.  Step through the “Installing the Seagate Software ABAP/4 Functions and Tables” procedures and ensure all the parameters were entered correctly.

Appendix 1 - Sample Services File Entries for SAP

sapdp00   3200/tcp
sapdp01   3201/tcp
sapdp02   3202/tcp
sapdp03   3203/tcp
sapdp04   3204/tcp
sapdp05   3205/tcp
sapdp06   3206/tcp
sapdp07   3207/tcp
sapdp08   3208/tcp
sapdp09   3209/tcp
sapdp10   3210/tcp
sapdp11   3211/tcp
sapdp12   3212/tcp
sapdp13   3213/tcp
sapdp14   3214/tcp
sapdp15   3215/tcp
sapdp16   3216/tcp
sapdp17   3217/tcp
sapdp18   3218/tcp
sapdp19   3219/tcp
sapdp20   3220/tcp
sapdp21   3221/tcp
sapdp22   3222/tcp
sapdp23   3223/tcp
sapdp24   3224/tcp
sapdp25   3225/tcp
sapdp26   3226/tcp
sapdp27   3227/tcp
sapdp28   3228/tcp
sapdp29   3229/tcp
sapdp30   3230/tcp
sapdp31   3231/tcp
sapdp32   3232/tcp
sapdp33   3233/tcp
sapdp34   3234/tcp
sapdp35   3235/tcp
sapdp36   3236/tcp
sapdp37   3237/tcp
sapdp38   3238/tcp
sapdp39   3239/tcp
sapdp40   3240/tcp
sapdp41   3241/tcp
sapdp42   3242/tcp
sapdp43   3243/tcp
sapdp44   3244/tcp
sapdp45   3245/tcp
sapdp46   3246/tcp
sapdp47   3247/tcp
sapdp48   3248/tcp
sapdp49   3249/tcp
sapdp50   3250/tcp
sapdp51   3251/tcp
sapdp52   3252/tcp
sapdp53   3253/tcp
sapdp54   3254/tcp
sapdp55   3255/tcp
sapdp56   3256/tcp
sapdp57   3257/tcp
sapdp58   3258/tcp
sapdp59   3259/tcp
sapdp60   3260/tcp
sapdp61   3261/tcp
sapdp62   3262/tcp
sapdp63   3263/tcp
sapdp64   3264/tcp
sapdp65   3265/tcp
sapdp66   3266/tcp
sapdp67   3267/tcp
sapdp68   3268/tcp
sapdp69   3269/tcp
sapdp70   3270/tcp
sapdp71   3271/tcp
sapdp72   3272/tcp
sapdp73   3273/tcp
sapdp74   3274/tcp
sapdp75   3275/tcp
sapdp76   3276/tcp
sapdp77   3277/tcp
sapdp78   3278/tcp
sapdp79   3279/tcp
sapdp80   3280/tcp
sapdp81   3281/tcp
sapdp82   3282/tcp
sapdp83   3283/tcp
sapdp84   3284/tcp
sapdp85   3285/tcp
sapdp86   3286/tcp
sapdp87   3287/tcp
sapdp88   3288/tcp
sapdp89   3289/tcp
sapdp90   3290/tcp
sapdp91   3291/tcp
sapdp92   3292/tcp
sapdp93   3293/tcp
sapdp94   3294/tcp
sapdp95   3295/tcp
sapdp96   3296/tcp
sapdp97   3297/tcp
sapdp98   3298/tcp
sapdp99   3299/tcp
sapgw00   3300/tcp
sapgw01   3301/tcp
sapgw02   3302/tcp
sapgw03   3303/tcp
sapgw04   3304/tcp
sapgw05   3305/tcp
sapgw06   3306/tcp
sapgw07   3307/tcp
sapgw08   3308/tcp
sapgw09   3309/tcp
sapgw10   3310/tcp
sapgw11   3311/tcp
sapgw12   3312/tcp
sapgw13   3313/tcp
sapgw14   3314/tcp
sapgw15   3315/tcp
sapgw16   3316/tcp
sapgw17   3317/tcp
sapgw18   3318/tcp
sapgw19   3319/tcp
sapgw20   3320/tcp
sapgw21   3321/tcp
sapgw22   3322/tcp
sapgw23   3323/tcp
sapgw24   3324/tcp
sapgw25   3325/tcp
sapgw26   3326/tcp
sapgw27   3327/tcp
sapgw28   3328/tcp
sapgw29   3329/tcp
sapgw30   3330/tcp
sapgw31   3331/tcp
sapgw32   3332/tcp
sapgw33   3333/tcp
sapgw34   3334/tcp
sapgw35   3335/tcp
sapgw36   3336/tcp
sapgw37   3337/tcp
sapgw38   3338/tcp
sapgw39   3339/tcp
sapgw40   3340/tcp
sapgw41   3341/tcp
sapgw42   3342/tcp
sapgw43   3343/tcp
sapgw44   3344/tcp
sapgw45   3345/tcp
sapgw46   3346/tcp
sapgw47   3347/tcp
sapgw48   3348/tcp
sapgw49   3349/tcp
sapgw50   3350/tcp
sapgw51   3351/tcp
sapgw52   3352/tcp
sapgw53   3353/tcp
sapgw54   3354/tcp
sapgw55   3355/tcp
sapgw56   3356/tcp
sapgw57   3357/tcp
sapgw58   3358/tcp
sapgw59   3359/tcp
sapgw60   3360/tcp
sapgw61   3361/tcp
sapgw62   3362/tcp
sapgw63   3363/tcp
sapgw64   3364/tcp
sapgw65   3365/tcp
sapgw66   3366/tcp
sapgw67   3367/tcp
sapgw68   3368/tcp
sapgw69   3369/tcp
sapgw70   3370/tcp
sapgw71   3371/tcp
sapgw72   3372/tcp
sapgw73   3373/tcp
sapgw74   3374/tcp
sapgw75   3375/tcp
sapgw76   3376/tcp
sapgw77   3377/tcp
sapgw78   3378/tcp
sapgw79   3379/tcp
sapgw80   3380/tcp
sapgw81   3381/tcp
sapgw82   3382/tcp
sapgw83   3383/tcp
sapgw84   3384/tcp
sapgw85   3385/tcp
sapgw86   3386/tcp
sapgw87   3387/tcp
sapgw88   3388/tcp
sapgw89   3389/tcp
sapgw90   3390/tcp
sapgw91   3391/tcp
sapgw92   3392/tcp
sapgw93   3393/tcp
sapgw94   3394/tcp
sapgw95   3395/tcp
sapgw96   3396/tcp
sapgw97   3397/tcp
sapgw98   3398/tcp
sapgw99   3399/tcp
sapsp00   3400/tcp
sapsp01   3401/tcp
sapsp02   3402/tcp
sapsp03   3403/tcp
sapsp04   3404/tcp
sapsp05   3405/tcp
sapsp06   3406/tcp
sapsp07   3407/tcp
sapsp08   3408/tcp
sapsp09   3409/tcp
sapsp10   3410/tcp
sapsp11   3411/tcp
sapsp12   3412/tcp
sapsp13   3413/tcp
sapsp14   3414/tcp
sapsp15   3415/tcp
sapsp16   3416/tcp
sapsp17   3417/tcp
sapsp18   3418/tcp
sapsp19   3419/tcp
sapsp20   3420/tcp
sapsp21   3421/tcp
sapsp22   3422/tcp
sapsp23   3423/tcp
sapsp24   3424/tcp
sapsp25   3425/tcp
sapsp26   3426/tcp
sapsp27   3427/tcp
sapsp28   3428/tcp
sapsp29   3429/tcp
sapsp30   3430/tcp
sapsp31   3431/tcp
sapsp32   3432/tcp
sapsp33   3433/tcp
sapsp34   3434/tcp
sapsp35   3435/tcp
sapsp36   3436/tcp
sapsp37   3437/tcp
sapsp38   3438/tcp
sapsp39   3439/tcp
sapsp40   3440/tcp
sapsp41   3441/tcp
sapsp42   3442/tcp
sapsp43   3443/tcp
sapsp44   3444/tcp
sapsp45   3445/tcp
sapsp46   3446/tcp
sapsp47   3447/tcp
sapsp48   3448/tcp
sapsp49   3449/tcp
sapsp50   3450/tcp
sapsp51   3451/tcp
sapsp52   3452/tcp
sapsp53   3453/tcp
sapsp54   3454/tcp
sapsp55   3455/tcp
sapsp56   3456/tcp
sapsp57   3457/tcp
sapsp58   3458/tcp
sapsp59   3459/tcp
sapsp60   3460/tcp
sapsp61   3461/tcp
sapsp62   3462/tcp
sapsp63   3463/tcp
sapsp64   3464/tcp
sapsp65   3465/tcp
sapsp66   3466/tcp
sapsp67   3467/tcp
sapsp68   3468/tcp
sapsp69   3469/tcp
sapsp70   3470/tcp
sapsp71   3471/tcp
sapsp72   3472/tcp
sapsp73   3473/tcp
sapsp74   3474/tcp
sapsp75   3475/tcp
sapsp76   3476/tcp
sapsp77   3477/tcp
sapsp78   3478/tcp
sapsp79   3479/tcp
sapsp80   3480/tcp
sapsp81   3481/tcp
sapsp82   3482/tcp
sapsp83   3483/tcp
sapsp84   3484/tcp
sapsp85   3485/tcp
sapsp86   3486/tcp
sapsp87   3487/tcp
sapsp88   3488/tcp
sapsp89   3489/tcp
sapsp90   3490/tcp
sapsp91   3491/tcp
sapsp92   3492/tcp
sapsp93   3493/tcp
sapsp94   3494/tcp
sapsp95   3495/tcp
sapsp96   3496/tcp
sapsp97   3497/tcp
sapsp98   3498/tcp
sapsp99   3499/tcp
sappcd    3500/tcp
sapmsC11       3600/tcp
sapmsD30       3607/tcp
sapmsD22       3622/tcp
sapmsHD3       3674/tcp
sapmsHDC       3675/tcp
sapmsH22       3676/tcp
sapmsQGG       3677/tcp
sapmsEGG       3678/tcp
sapmsFMT       3679/tcp
sapmsISV       3680/tcp
sapmsCER       3681/tcp
sapinfI22      3800/tcp       informix
sapinfC20      3801/tcp       informix
sapinfC30      3802/tcp       informix
sapinfC50      3803/tcp       informix
sapedi4        3995/tcp    # R/3 EDI-Konverter-Thomas Becker
sapedi3        3996/tcp    # R/3 EDI Konverter-Thomas Becker
sapedi2        3997/tcp    # R/3 EDI Konverter-Thomas Becker
sapedi1        3998/tcp    # R/3 EDI Konverter Texas Instruments-Thomas Becker
sapedi0        3999/tcp    # R/3 EDI Konverter Texas Instruments-Thomas Becker
sapgw           22102/tcp sapgw-bc              # TTRS Service